chore: sync release-please manifest to 3.2.0#77
Merged
Conversation
Manual tag v3.2.0 was pushed to trigger release.yml → PyPI publish after the stacked 3.1/3.1.1/3.1.2/3.2 release PR (#74) merged. This bumps the manifest so the next release-please cycle starts from 3.2.0 instead of trying to bridge 3.0.0 → next across 12 commits.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
After merging #74 and pushing the
v3.2.0tag manually to triggerrelease.yml→ PyPI publish, bump the release-please manifest so the next cycle knows where we are. Otherwise release-please would scan all 12 commits sincev3.0.0and (givenfeat!:in the stack) proposev4.0.0.Test plan
.release-please-manifest.jsonupdated to match the pushed tagv3.2.0.280 passed, 18 skipped.